Add basic proguard config for module framework targets Most module framework libs do not enable optimization, but several do, and there is increasing interest in expanding this set. Add a basic set of `-keepattributes` rules that will be inherited by all module java_sdk_library targets, and used if/when R8 optimization is enabled. This is particularly important as we transition to using R8 full mode by default, as it's far more aggressive about stripping attributes (e.g., signatures) that might be critical for library targets w/ public APIs. Bug: 215530220 Bug: 349177664 Flag: EXEMPT very low risk safeguard to ensure kept attributes Test: m + apkdiffstats Test: cts/tests/signature/runSignatureTests.sh Change-Id: I26a0509252987b0d5a098d4de7933245355e9d1f 
3 files changed
tree: d190b276c665dc0112a0d3c1d13e30cd1b651043
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.